home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #14
/
Monster Media No. 14 (April 1996) (Monster Media, Inc.).ISO
/
netmail
/
tgwav112.zip
/
WHATSNEW.110
< prev
next >
Wrap
Text File
|
1995-12-15
|
14KB
|
265 lines
┌── · ▄▄▄. ──────────────────────────────────────────────────────┼--
│ .■▄█▀▀▀▀■. TGWave v1.10 - WHATS NEW IN THIS VERSION │
■▄█░█▒ · ▄ Copyright 1995 Lars Hellsten, All Rights Reserved │
░███████▄▄▄▄██ Another great MatrixSoft product! │
┌────────────────────────────────────────────────────────────────┐
└───── Blue Wave / QWK offline mail door for Telegard v2.99 ─────┘
This file contains a list of major changes that have been made since
the first release of TGWave. It is best when upgrading to a new
version, to search this file for the release of the version you're
currently running, and then read *UP* from that point. That way you
see the changes in the order they were made.
IMPORTANT: If there have been any changes to strings in the language
file between this version and the last version you were running, you
MUST update your ENGLISH.TGW file and recompile! Either that, or
replace the file with the new default file in the \SAMPLES\ directory.
Remember to recompile using TGWLCOMP. You will also want to replace
your TEXT\*.TPL files with
HISTORY - BUGS FIXED, CHANGES MADE, ETC.
%=Bug Fix / +=New Feature / *=Updated Feature / !=Note
[12/25/95 - v1.10 released]
* Strings to be removed from the language file:
070 `07TGWave will now keep your area selections the same as in Telegard.~SM~SM~SP
071 `07Your TGWave area selections will now be kept separate from your Telegard~SMQWK area selections.~SM~SM~SP
145 ADD
146 DROP
147 RESET
I decided to make the QWK offline configuration commands hard-
coded. Aside from the novelty, the configurability is pointless -
these names are the de-facto standards, and the sysop them would
accomplish little other than confuse users and their QWK readers.
Strings to be added/updated:
019 `09■ `0BImporting your current Telegard QWK area selections; please wait ...
052 `0C~SMContinue? [No]: `0B
066 `09Area `0A#~&1 `09"`0B~ES~MB`09" ignored - conference is forced.~SM
067 `09Area `0A#~&1 `09"`0B~ES~MB`09" WILL be scanned.~SM
068 `09Area `0A#~&1 `09"`0B~ES~MB`09" will NOT be scanned.~SM
070 `09Area `0A#~&1 `09"`0B~ES~MB`09" - personal+"All" messages will be bundled.~SM
071 `09Area `0A#~&1 `09"`0B~ES~MB`09" - only keywords will be bundled.~SM
075 `09Area `0A#~&1 `09"`0B~ES~MB`09" - filters enabled.~SM
076 `09Area `0A#~&1 `09"`0B~ES~MB`09" - personal messages will be bundled.~SM
073 ■PAKF-! <- Characters used for "status" field in area listings
074 For
142 -\|/
* TGWave will now look for GROUPS.DAT. If it doesn't exist, it
will then try and use CONFRENC.DAT.
+ Kludge lines (any line beginning with ^A/ASCII-1) are now
stripped from Squish bases.
* TGWave now adds the ^AMSGID: and ^APID: kludges.
+ TGWave now traps CTRL-C and CTRL-BREAK, so you can't accidentaly
press them and have the program bomb out when it's in the middle
of doing something like updating lastread pointers, or whatnot.
% PRESCAN mode now properly detects the personal/keyword/filter
status of messages - it was marking all messages with no (regular)
status.
% Aborting (spacebar, ^K, ^X) now works with Squish bases when
scanning.
+ Added a "twirly thing" as a progress indicator when scanning the
message areas. The following string should be added to your
language file:
142 -\|/
* Changed the intro screen to something that looks a little sleeker
and more professional (I think). Thanks to Tom Klepl (PCBWave beta
tester) for this new version of the logo.
% ~*H MCI code should work in the ENGLISH.TWC file, and the ~*X
code has been changed to ~*T, with ~*T being changed to ~*Z or
something.
% TGWave wasn't processing certain ACS strings properly, such as
Gx, I##-####, etc. All ACS strings should be processed fine now,
the ACS parsing routines just weren't updated to handle certain
tokens properly.
+ TGWAVE now has a seamless Internet support feature. There is now
an "Internet Gateway Configuration" menu in TGWSETUP, where you
can configure TGWAVE's Internet gateway setup.
This seamlessly integrates Internet e-mail support into the user's
offline mail packet. If the gateway support is enabled, TGWAVE
will insert an e-mail area in the user's packet. Users can post
to the e-mail area, using long "To:" names (up to 75+ characters),
without having to enter the netmail address of the Internet
gateway, or worry about putting "To: <address>" on the first line
of the message. Now TGWave handles all that itself.
If a user uploads a reply packet with a message to the e-mail area,
TGWAVE will reformat the message according to your Internet gateway
configuration, and post it in the destination netmail area (also
defined in the gateway configuration menu).
Please note that this feature is only for outgoing Internet e-mail
messages. The user will still need to scan your netmail base (or
whatever) if they want to download incoming e-mail and read it
offline.
+ Major changes to the way TGWAVE handles area selections. This is
done to provide compatibility with the new v2.20 reader's features,
as well as more flexibility to the reader.
(1) The option of internal/external scan information is no longer
provided - TGWAVE uses it's SCANINFO.TGW file for everything,
period.
(2) The P, A, F, K and E bundling commands permanently affect the
user's selected areas. The P, A, F and K options are also
now available from the area selection menu, used in the same
format as the "+", "-" commands - "P##", "P##-##", "P*", etc.
(3) "Internal base selection" option in the variables/limits
menu in TGWSETUP has been removed, since it is no longer
used. As a result, the ~!Z MCI code and option 15 of the &T
menu command are also removed.
(4) If you were not using the Internal scan info (SCANINFO.TGW)
option, on your system, all message area selections will be
lost for all users. I'm sorry about this, but the only away
around it would be for INSTALL to go through every *.MSI file
for every TGWave user and pull out their message area
selections - some thing I didn't want to code, and that would
make the upgrade to v1.02 very slow.
I should have forseen this, and had TGWave up date the
SCANINFO.TGW file in addition to the *.MSI files, regardless
of the settings, but c'est la vie. I suggest simply telling
your users to have Blue Wave include their configuration with
the packet - then they can simply upload their area selections
and everything will be reconfigured the way it was before.
For these changes, several strings had to be changed in the lang-
uage file. You will need to either replace your ENGLISH.TGW file
with the new default one from the SAMPLES\ directory, or if
you've customized your language file, simply copy the new strings
in, and delete the old ones.
+ Added "Import TG scan info" to the TGWSETUP variables/limits menu.
This is to replace the "Internal base selection" option which was
removed. If set to "Yes", TGWAVE will import the area config for
new TGWAVE users from Telegard's settings (as set by the MZ and
QZ menu commands). See the online help entry for a more detailed
description.
+ TGWAVE now supports the Blue Wave reader v2.20 offline config
features. The 2.12 format/features are still supported, but
TGWAVE now tells the reader that it's compatible with the new
features, and supports the new .OLC offline configuration data
file and most of the advanced offline configuration features.
+ TGWave will now process QWK offline configuration requests that
are addressed to one of the following names: "TELEGARD", "QMAIL",
"ROSEMAIL" (case-insensitive), in addition to "TGWAVE".
+ Added the following QWK offline configuration commands. Like the
ADD, DROP and RESET commands, the message should be addressed to
"TGWAVE" in the area the changes are to take effect. Multiple
formats of each command are supported for maximum compatibility,
since many QWK doors have their own way of doing it - TGWave uses
the all the formats of the most popular QWK doors.
"ADD YOURS" ┐ Selects the area,
"ADD Y" ├ toggles it to personal
"YOURS" ┘ messages only.
"ADD YA" ┐ Selects the area, toggles it
"YOURS ALL" ├ to personal messages, and messages
"YA" ┘ to "All" only.
+ Added the following paths that can be configured:
\TEXT\ TGWave text/display/template files
\HELP\ TGWave help directory
\LANGUAGE\ TGWave language files
These allow you to split up TGWave's needed files, rather than
having everything all lumped into your \MENUTEXT\ directory.
INSTALL will point these directories all to your current MENUS
and TEXT directory to keep this version compatible with your old
setup, but should you wish to split the directories up, you may
do so.
% TGWave works properly with Squish bases now. Both Telegard and
TGWave would process TGWave's messages properly, but it seems
Squish (the tosser) is VERY picky, and there were a couple of
things TGWave was doing that Squish did not like. Squish should
now export messages posted from TGWave properly.
% The keyboard buffer is now cleared when a user aborts something,
so that if the spacebar is hit quickly, say, 5 times, it won't
display the main menu 5 times and then abort it each time, which
was annoying with the default "Aborted" string which has two
~SW MCI codes in it.
% TGWave no longer reformats the "To:" field when posting with the
user's alias. I was used to the old system, and forgot to take
into account that Telegard v2.99 supports aliases in mixed/any
case, rather than all caps.
% Fixed the reset lastread pointers menu command (it actually works
this time ... )
% MCI code justification now properly justifies MCI codes with
embedded color codes - it was taking the colour codes as though
they were part of the string when padding.
% MCI justification codes (~ELxx, etc.) no longer require leading
zeros - "~EL5" will now work, as well as "~EL05".
* The message area names are now passed WITH color codes to the
area selection template ~&c MCI code, as opposed to that MCI code
being the area name with colors stripped.
% TGWAVE will now work properly on JAM/Squish bases if SHARE is
not installed. Before it was frequently trying to lock messages,
and timing out if it couldn't lock them, without checking if
SHARE is installed. If SHARE is not installed it will now not
attempt to lock the message areas.
Technically, the JAM specifications state that the JAM data
files MUST be opened by programs in shared mode. But TGWAVE now
ignores this due to complications that may arise with certain
operating systems/environments. If SHARE is not detected, it
will not attempt to lock the message base data files.
If you are running multi-node, please ensure that SHARE *IS*
installed. Under some OS's, it may be necessary to run programs
like FAKESHARE to trick software into thinking SHARE is instal-
led. TGWAVE reports something like "Running with SHARE under
Windows v4.00" in the log files if it detects SHARE.
* The door now supports the ~CI and ~CJ MCI codes for IRQ and base
address (needed for non-standard IRQ setups with DSZ/GSZ), and
improved/optimized MCI code parsing a bit.
* Sped up scanning even faster on JAM bases, by using the memory
allocated to the message text buffer (since it only needs it when
bundling) to buffer reading of the .JDX files. Also, it now reads
all subfield data into a buffer in one pass, rather than reading
each one separately. A few other miscellaneous speed improvements
were made here as well.
[09/07/95 - v1.01 released]